docs: simplify $effect.tracking() docs
#14939
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Member
Author
|
preview: https://svelte-dev-git-preview-svelte-14939-svelte.vercel.app/ this is an automated message |
Contributor
|
trueadm
approved these changes
Jan 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
while reviewing #14821, I realised that the
$effect.tracking()docs come across a bit strangely now that we havecreateSubscriber. I think it makes more sense to just link to those docs to explain the purpose of the rune, rather than laboriously recreating a worse version of the abstraction (which someone might, seeing those docs, decide to use).It also means that we're spending less real estate on an extremely niche feature that most people shouldn't be touching